[fix]: fixed edge case crash cases if notifications are processed nearly simultaneously #2946
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link the issue which is closed by this PR
Implementation details
In #2944 a controller crash occured if notifications were cleaned nearly simultaneously, and we only checked that the index is present at the beginning of the file and not re-checked after doing asynchronous operation. Hence, we added
noUncheckedIndexedAccess
for the tsconfig (onlycommon
package) to avoid these cases.Tests
If no tests added, please specify why it was not possible
Not really possible, but we avoided these cases by adapting the tsconfig for adding
noUncheckedIndexedAccess
rule for this file.